-
Notifications
You must be signed in to change notification settings - Fork 519
Align categories #15801
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Align categories #15801
Conversation
🚀 Benchmarks reportTo see the full report comment with |
|
@elastic/security-service-integrations @elastic/obs-ds-hosted-services @elastic/obs-infraobs-integrations could you please look into it? |
andrewkroh
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM.
For each policy template category, I determined its parent category (or considered it its own parent if it wasn't a subcategory). Then, I validated that these derived parent categories were all present in the integration package's categories. Then I checked that the parent categories of policy template categories are a subset of package categories. I checked all integrations present in 5245547.
The category relationships I used are given in https://github.com/elastic/package-registry/blob/1bec8bf2e7f67f04f38a6310f5b70e56e3b22bfd/categories/categories.yml
|
I think proposed commit message could use a deeper explanation. And we should refer to "policy template" instead of "datastreams". Suggestion: That doesn't answer the why behind this change so you should add that. |
|
@uri-weisman could you please check this PR as a maintainer of @elastic/contextual-security |
uri-weisman
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
💚 Build Succeeded
History
|
…lastic#15801) This commit addresses inconsistencies in package categorization by adding missing categories to various integration packages. Previously, policy templates within certain integrations used categories (or their parent categories) that were not explicitly defined at the integration level. This was identified by ensuring all parent categories of policy template categories are a subset of integration-level categories. References https://github.com/elastic/package-registry/blob/1bec8bf2e7f67f04f38a6310f5b70e56e3b22bfd/categories/categories.yml
This PR aligns categories from data_streams in templates with global categories of the integration.
Proposed commit message
Aligning categories of sub datastreams with category of integration itself.
Issues:
was discussed in https://github.com/elastic/protections-cloud/issues/15713
@jsoriano @JDKurma FYI